Move NEWS entries to pull-request-lifecycle#1506
Move NEWS entries to pull-request-lifecycle#1506StanFromIreland wants to merge 10 commits intopython:mainfrom
Conversation
This reverts commit 6860013.
|
See also would be nice but it seems to make the section quoted. |
hugovk
left a comment
hugovk
left a comment
There was a problem hiding this comment.
See also would be nice but it seems to make the section quoted.
How do you mean?
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
I must have done something weird before it works when I tried again! |
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
There was a problem hiding this comment.
We improved a bit the content, but not by much, so it's fine to make it part of this change. I think we need a follow-up PR to improve the cases where a NEWS entry is necessary (see python/cpython#131177 (comment)). OTOH, you can revert the 3.X.rst mention and make it part of the follow-up PR.
Before merging, I'll check that the rst:role is correctly linked though.
|
Arf, it appears that we don't have the cross-referencing:
Well, let's introduce intersphinx in a future PR. |
# Conflicts: # core-team/committing.rst
|
Closed the originally linked issue as a duplicate of #674 |
3 participants
Fixes #674 (and duplicate #1242).
📚 Documentation preview 📚: https://cpython-devguide--1506.org.readthedocs.build/getting-started/pull-request-lifecycle/#what-s-new-and-news-entries